Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Clarify single-removal behavior in trimsuffix and trimprefix docs into v1.10 #36042

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Backport

This PR is auto-generated from #35900 to be assessed for backporting due to the inclusion of the label 1.10-backport.

The below text is copied from the body of the original PR.


The doc was not so clear if the suffix was removed multiple times. There is a difference in behavior to trim. The documentation is clarified with this MR.

Target Release

1.10.x

Draft CHANGELOG entry

Doc Update

  • Clarify single-removal behavior in trimsuffix and trimprefix docs

Overview of commits

@github-actions github-actions bot force-pushed the backport/main/quickly-desired-filly branch from 3eb72db to 975ff1d Compare November 18, 2024 23:40
@github-actions github-actions bot requested a review from crw November 18, 2024 23:40
@crw crw marked this pull request as ready for review November 18, 2024 23:41
@crw crw merged commit dda67dd into v1.10 Nov 18, 2024
6 checks passed
@crw crw deleted the backport/main/quickly-desired-filly branch November 18, 2024 23:54
Copy link
Contributor Author

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Copy link
Contributor Author

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants